Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated README.md #6182

Merged
merged 3 commits into from
Dec 16, 2024
Merged

Updated README.md #6182

merged 3 commits into from
Dec 16, 2024

Conversation

danciaclara
Copy link
Collaborator

@danciaclara danciaclara commented Dec 10, 2024

Summary by CodeRabbit

Summary by CodeRabbit

  • Documentation
    • Enhanced readability and structure of the README.md.
    • Updated installation instructions for Plane Cloud and self-hosting.
    • Improved features section with more descriptive bullet points.
    • Expanded community engagement and contributing sections.
    • Added a license section specifying GNU Affero General Public License v3.0.

Copy link
Contributor

coderabbitai bot commented Dec 10, 2024

Walkthrough

The README.md file has been extensively revised to enhance content clarity and structure. Key updates include a change of the title to an <h1> for better visibility, improved installation instructions for both Plane Cloud and self-hosting options, and a restructured local development section. The community engagement and security sections have been expanded and formalized, respectively. Additionally, the contributing guidelines have been clarified, and a new license section specifies the project's licensing under the GNU Affero General Public License v3.0.

Changes

File Change Summary
README.md - Changed title from <h3> to <h1>.
- Enhanced introductory description.
- Updated installation section with clearer instructions and new headings.
- Added updated documentation links for Docker and Kubernetes in the installation methods table.
- Clarified instance administrator management settings.
- Reformatted features section with more descriptive bullet points.
- Restructured local development section with new headings for prerequisites and setup.
- Expanded community engagement section.
- Updated security section for reporting vulnerabilities.
- Revised contributing section to outline various contribution methods.
- Added license section specifying GNU Affero General Public License v3.0.

Possibly related PRs

  • Updated SECURITY.md #5737: The changes in the SECURITY.md file regarding community involvement in reporting vulnerabilities complement the updates made in README.md, particularly in the sections about community engagement and security reporting.

🐇 In a garden where ideas bloom,
The README shines, dispelling gloom.
With clearer paths and guidance bright,
Contributors gather, ready to write.
Join the dance, let voices blend,
In this project, all can lend! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (5)
README.md (5)

5-5: Consider using a CDN-hosted static image URL

The current logo URL uses Next.js's image optimization route (_next/image), which might not be ideal for a README file as it:

  1. Depends on the Next.js server being available
  2. May not work properly when viewed on GitHub or other platforms

Consider hosting the logo on a CDN or using a direct static image URL from your repository:

-  <img src="https://plane.so/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fplane-logo-with-text.31443952.png&w=640&q=75" alt="Plane Logo" width="300">
+  <img src="https://plane-marketing.s3.ap-south-1.amazonaws.com/plane-logo-with-text.png" alt="Plane Logo" width="300">

63-79: Maintain consistent punctuation in feature descriptions

Some feature descriptions end with periods while others don't. Let's maintain consistency:

- Simplify complex projects by dividing them into smaller, manageable modules. 
+ Simplify complex projects by dividing them into smaller, manageable modules.

90-111: Add language specifications to code blocks

For better syntax highlighting and documentation consistency, specify the language for each code block:

-   ```
+   ```bash
    git clone https://github.com/makeplane/plane.git
    ```

Apply this to all command blocks in the local development section.

🧰 Tools
🪛 Markdownlint (0.35.0)

91-91: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


95-95: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


99-99: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


103-103: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


111-111: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


204-204: Add alt text to contributor image

For better accessibility, add descriptive alt text to the contributor image:

- <img src="https://contrib.rocks/image?repo=makeplane/plane" />
+ <img src="https://contrib.rocks/image?repo=makeplane/plane" alt="Plane GitHub contributors" />
🧰 Tools
🪛 Markdownlint (0.35.0)

204-204: null
Images should have alternate text (alt text)

(MD045, no-alt-text)


176-178: Enhance writing style in community section

Consider these style improvements for a more professional tone:

- Feel free to ask questions, report bugs, participate in discussions
+ We encourage you to ask questions, report bugs, participate in discussions
🧰 Tools
🪛 LanguageTool

[style] ~177-~177: The phrase ‘feel free to’ is used quite frequently. Consider using a less frequent alternative to set your writing apart from others and make it sound more professional.
Context: ...UCT.md) in all our community channels. Feel free to ask questions, report bugs, participate...

(FEEL_FREE_TO_STYLE_ME)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f06b1b8 and a80423a.

📒 Files selected for processing (1)
  • README.md (3 hunks)
🧰 Additional context used
🪛 Markdownlint (0.35.0)
README.md

87-87: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


91-91: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


95-95: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


99-99: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


103-103: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


111-111: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


201-201: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


184-184: null
Bare URL used

(MD034, no-bare-urls)


204-204: null
Images should have alternate text (alt text)

(MD045, no-alt-text)

🪛 LanguageTool
README.md

[style] ~177-~177: The phrase ‘feel free to’ is used quite frequently. Consider using a less frequent alternative to set your writing apart from others and make it sound more professional.
Context: ...UCT.md) in all our community channels. Feel free to ask questions, report bugs, participate...

(FEEL_FREE_TO_STYLE_ME)


[style] ~192-~192: This expression usually appears with a “please” in front of it.
Context: ...or any other ecosystem integration and let us know...

(INSERT_PLEASE)

🔇 Additional comments (2)
README.md (2)

44-59: LGTM! Well-structured installation section

The installation section effectively presents both cloud and self-hosted options with clear documentation links and setup guidance.


180-209: LGTM! Comprehensive security and contribution guidelines

The section effectively covers security reporting, contribution guidelines, and licensing information.

🧰 Tools
🪛 LanguageTool

[style] ~192-~192: This expression usually appears with a “please” in front of it.
Context: ...or any other ecosystem integration and let us know...

(INSERT_PLEASE)

🪛 Markdownlint (0.35.0)

201-201: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


184-184: null
Bare URL used

(MD034, no-bare-urls)


204-204: null
Images should have alternate text (alt text)

(MD045, no-alt-text)

@plane-bot plane-bot marked this pull request as draft December 10, 2024 19:45
@sriramveeraghanta sriramveeraghanta marked this pull request as ready for review December 16, 2024 09:01
@sriramveeraghanta sriramveeraghanta merged commit 1119b9d into preview Dec 16, 2024
20 of 22 checks passed
@sriramveeraghanta sriramveeraghanta deleted the update-readme branch December 16, 2024 09:03
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (7)
README.md (7)

45-60: Consider adding version information to installation guides.

While the installation section is well-structured, adding minimum version requirements for Docker and Kubernetes would help users prepare their environment better.

| Installation methods | Requirements | Docs link |
| ------------------- | ------------ | --------- |
-| Docker             | | [![Docker](https://img.shields.io/badge/docker-%230db7ed.svg?style=for-the-badge&logo=docker&logoColor=white)](https://developers.plane.so/self-hosting/methods/docker-compose) |
+| Docker             | Docker Engine 20.10.0+ | [![Docker](https://img.shields.io/badge/docker-%230db7ed.svg?style=for-the-badge&logo=docker&logoColor=white)](https://developers.plane.so/self-hosting/methods/docker-compose) |
-| Kubernetes         | | [![Kubernetes](https://img.shields.io/badge/kubernetes-%23326ce5.svg?style=for-the-badge&logo=kubernetes&logoColor=white)](https://developers.plane.so/self-hosting/methods/kubernetes) |
+| Kubernetes         | Kubernetes 1.19+ | [![Kubernetes](https://img.shields.io/badge/kubernetes-%23326ce5.svg?style=for-the-badge&logo=kubernetes&logoColor=white)](https://developers.plane.so/self-hosting/methods/kubernetes) |

62-82: Make the "coming soon" feature more prominent.

Consider using a different formatting style to make the Drive feature's status more noticeable:

-- **Drive** (_coming soon_): The drive helps you share documents...
+### 🚧 Coming Soon
+- **Drive**: The drive helps you share documents...

93-114: Add language specifiers to code blocks for better readability.

The code blocks should specify their language for proper syntax highlighting:

-   ```
+   ```bash
    git clone https://github.com/makeplane/plane.git
    ```

-   ```
+   ```bash
    cd plane
    ```

-   ```
+   ```bash
    git checkout -b <feature-branch-name>
    ```

-   ```
+   ```bash
    ./setup.sh
    ```

-   ```
+   ```bash
    docker compose -f docker-compose-local.yml up -d
    ```
🧰 Tools
🪛 Markdownlint (0.37.0)

94-94: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


98-98: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


102-102: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


106-106: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


114-114: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


120-123: Improve badge layout efficiency.

Consider displaying the technology stack badges in a single line for better space utilization:

-[![Next JS](https://img.shields.io/badge/next.js-000000?style=for-the-badge&logo=nextdotjs&logoColor=white)](https://nextjs.org/)<br/>
-[![Django](https://img.shields.io/badge/Django-092E20?style=for-the-badge&logo=django&logoColor=green)](https://www.djangoproject.com/)<br/>
-[![Node JS](https://img.shields.io/badge/node.js-339933?style=for-the-badge&logo=Node.js&logoColor=white)](https://nodejs.org/en)
+[![Next JS](https://img.shields.io/badge/next.js-000000?style=for-the-badge&logo=nextdotjs&logoColor=white)](https://nextjs.org/)
+[![Django](https://img.shields.io/badge/Django-092E20?style=for-the-badge&logo=django&logoColor=green)](https://www.djangoproject.com/)
+[![Node JS](https://img.shields.io/badge/node.js-339933?style=for-the-badge&logo=Node.js&logoColor=white)](https://nodejs.org/en)

216-216: Add alt text to contributor images for accessibility.

The contributor image is missing alt text:

-  <img src="https://contrib.rocks/image?repo=makeplane/plane" />
+  <img src="https://contrib.rocks/image?repo=makeplane/plane" alt="Plane GitHub contributors" />
🧰 Tools
🪛 Markdownlint (0.37.0)

216-216: null
Images should have alternate text (alt text)

(MD045, no-alt-text)


189-190: Enhance the writing style in the community section.

Consider rephrasing for a more professional tone:

-Feel free to ask questions, report bugs, participate in discussions, share ideas, request features, or showcase your projects.
+We welcome your questions, bug reports, discussion participation, ideas, feature requests, and project showcases.
🧰 Tools
🪛 LanguageTool

[style] ~189-~189: The phrase ‘feel free to’ is used quite frequently. Consider using a less frequent alternative to set your writing apart from others and make it sound more professional.
Context: ...UCT.md) in all our community channels. Feel free to ask questions, report bugs, participate...

(FEEL_FREE_TO_STYLE_ME)


196-196: Encode the security email address to prevent scraping.

Consider encoding the email address to reduce spam:

-To disclose any security issues, please email us at [email protected].
+To disclose any security issues, please email us at <a href="mailto:&#115;&#101;&#99;&#117;&#114;&#105;&#116;&#121;&#64;&#112;&#108;&#97;&#110;&#101;&#46;&#115;&#111;">security[at]plane.so</a>.
🧰 Tools
🪛 Markdownlint (0.37.0)

196-196: null
Bare URL used

(MD034, no-bare-urls)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a80423a and 4b676b2.

📒 Files selected for processing (1)
  • README.md (4 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
README.md

90-90: null
Multiple spaces after hash on atx style heading

(MD019, no-multiple-space-atx)


94-94: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


98-98: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


102-102: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


106-106: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


114-114: null
Fenced code blocks should have a language specified

(MD040, fenced-code-language)


213-213: Punctuation: '.'
Trailing punctuation in heading

(MD026, no-trailing-punctuation)


196-196: null
Bare URL used

(MD034, no-bare-urls)


216-216: null
Images should have alternate text (alt text)

(MD045, no-alt-text)

🪛 LanguageTool
README.md

[style] ~189-~189: The phrase ‘feel free to’ is used quite frequently. Consider using a less frequent alternative to set your writing apart from others and make it sound more professional.
Context: ...UCT.md) in all our community channels. Feel free to ask questions, report bugs, participate...

(FEEL_FREE_TO_STYLE_ME)


[style] ~204-~204: This expression usually appears with a “please” in front of it.
Context: ...or any other ecosystem integration and let us know...

(INSERT_PLEASE)

🔇 Additional comments (1)
README.md (1)

Line range hint 8-24: LGTM! Header section is well-structured.

The header section improvements, including the h1 title and comprehensive badges, enhance visibility and provide quick access to important resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants